Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d21d625c707852eed4e7e41bbb40cb071c3084ad1c154825cfede67dbfd0edca

Tx prefix hash: d80da23997fc37fc8c2e0ad7b57e6a3dc091aa9c3bc17ccb052b832bdddecc97
Tx public key: 45fa017210d08a93a32c46de526df4bc04b315e57e196097d209f3838cf14a33
Timestamp: 1708821845 Timestamp [UCT]: 2024-02-25 00:44:05 Age [y:d:h:m:s]: 01:046:03:04:47
Block: 964890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293984 RingCT/type: yes/0
Extra: 0145fa017210d08a93a32c46de526df4bc04b315e57e196097d209f3838cf14a3302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65b38ddc70491f4456f6c06fac2e188cbfa5e6b6b3f5608c2b072830e0a206a5 0.600000000000 1424633 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": 964900, "vin": [ { "gen": { "height": 964890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65b38ddc70491f4456f6c06fac2e188cbfa5e6b6b3f5608c2b072830e0a206a5" } } ], "extra": [ 1, 69, 250, 1, 114, 16, 208, 138, 147, 163, 44, 70, 222, 82, 109, 244, 188, 4, 179, 21, 229, 126, 25, 96, 151, 210, 9, 243, 131, 140, 241, 74, 51, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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