Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a499f4bc80e9e7914ea3198ae4950a581e5ded2251b714bb410f8994b4e4e3c7

Tx prefix hash: 097385406dbffd813e87cde9f407f3d32adf5441aa75d0963495c277596c384b
Tx public key: b96c605d296c515eb9e9228fab3bfef1d1b311d6e99de651d83245eaaf8dd463
Timestamp: 1728169549 Timestamp [UCT]: 2024-10-05 23:05:49 Age [y:d:h:m:s]: 00:177:10:27:19
Block: 1125289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126593 RingCT/type: yes/0
Extra: 01b96c605d296c515eb9e9228fab3bfef1d1b311d6e99de651d83245eaaf8dd46302110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c85faa86cf155e45b7174021eafe8bfcaeaf9eb412bb51e4db8b13717dad6f81 0.600000000000 1607966 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": 1125299, "vin": [ { "gen": { "height": 1125289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c85faa86cf155e45b7174021eafe8bfcaeaf9eb412bb51e4db8b13717dad6f81" } } ], "extra": [ 1, 185, 108, 96, 93, 41, 108, 81, 94, 185, 233, 34, 143, 171, 59, 254, 241, 209, 179, 17, 214, 233, 157, 230, 81, 216, 50, 69, 234, 175, 141, 212, 99, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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