Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 010a7d880cb1a31fdf492f9f3c51bcea8b078a0d7b30f98fd0155476e7bf075d

Tx prefix hash: eb17dc149465ba898e8dbdd13472c29427efc36996aa4b981d7915dc02053481
Tx public key: adc4b5b44ab6a0743774f1f981a725b601e35af5ff69d49d577fd23c1b0c6584
Timestamp: 1706629916 Timestamp [UCT]: 2024-01-30 15:51:56 Age [y:d:h:m:s]: 01:066:04:04:13
Block: 946688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308374 RingCT/type: yes/0
Extra: 01adc4b5b44ab6a0743774f1f981a725b601e35af5ff69d49d577fd23c1b0c65840211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13757dcf5a40c832e7ff9eefb74d29eec4ed429ca033c21df9d711179565a41c 0.600000000000 1405022 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 946698, "vin": [ { "gen": { "height": 946688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13757dcf5a40c832e7ff9eefb74d29eec4ed429ca033c21df9d711179565a41c" } } ], "extra": [ 1, 173, 196, 181, 180, 74, 182, 160, 116, 55, 116, 241, 249, 129, 167, 37, 182, 1, 227, 90, 245, 255, 105, 212, 157, 87, 127, 210, 60, 27, 12, 101, 132, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8