Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 221baabf3cf2a398fc39fcf7af623fc89d12f7d4b81031acfd0d4b62b2ea63eb

Tx prefix hash: c1986597480501f8f39a18d9d6faa26b4eaa8f6fecc948441aaaad7e07f45e4d
Tx public key: b71da145f47c22ec3630281a81aaa69f1571007d95ae1f2db7f4bab1f4f29751
Timestamp: 1737974516 Timestamp [UCT]: 2025-01-27 10:41:56 Age [y:d:h:m:s]: 00:046:05:22:24
Block: 1206179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33054 RingCT/type: yes/0
Extra: 01b71da145f47c22ec3630281a81aaa69f1571007d95ae1f2db7f4bab1f4f297510211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 618b766c4a3dcf4b4630c4b4f514f352aee119560a2cf9e1eed4b53dfdf9e129 0.600000000000 1692882 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": 1206189, "vin": [ { "gen": { "height": 1206179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "618b766c4a3dcf4b4630c4b4f514f352aee119560a2cf9e1eed4b53dfdf9e129" } } ], "extra": [ 1, 183, 29, 161, 69, 244, 124, 34, 236, 54, 48, 40, 26, 129, 170, 166, 159, 21, 113, 0, 125, 149, 174, 31, 45, 183, 244, 186, 177, 244, 242, 151, 81, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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