Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8179871440c9dc68b408ff5254fd0d40e042f0be15f0a90b28ff334471391b70

Tx prefix hash: 594f86e1d727d31a5519bf335a9ba3c4f472ce7a8838f62ab56a7a212bbb4083
Tx public key: d7658c9acf1700f8d25d1b4c0061a2d2b0023342766c1b24a828bb72968a3a04
Timestamp: 1727574902 Timestamp [UCT]: 2024-09-29 01:55:02 Age [y:d:h:m:s]: 00:167:16:22:45
Block: 1120357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119661 RingCT/type: yes/0
Extra: 01d7658c9acf1700f8d25d1b4c0061a2d2b0023342766c1b24a828bb72968a3a0402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1db243ba04661f0cf70dae86c4ec481f36737c1614e083108b973dbf31ddba01 0.600000000000 1602242 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": 1120367, "vin": [ { "gen": { "height": 1120357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1db243ba04661f0cf70dae86c4ec481f36737c1614e083108b973dbf31ddba01" } } ], "extra": [ 1, 215, 101, 140, 154, 207, 23, 0, 248, 210, 93, 27, 76, 0, 97, 162, 210, 176, 2, 51, 66, 118, 108, 27, 36, 168, 40, 187, 114, 150, 138, 58, 4, 2, 17, 0, 0, 0, 5, 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