Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d04ef445de9608bc67e2fa2ed15b3f6e9fd0bece8328098f4798fcbcc28c680b

Tx prefix hash: 64758a802107e92d17b277a399d86aa8c8d702890e5a2e925490ee53107f8805
Tx public key: b14d52de3c159722e299e535a7a16c8d56078e4fd67b33cfc57443d0e864885d
Timestamp: 1733612854 Timestamp [UCT]: 2024-12-07 23:07:34 Age [y:d:h:m:s]: 00:118:03:33:11
Block: 1170318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84222 RingCT/type: yes/0
Extra: 01b14d52de3c159722e299e535a7a16c8d56078e4fd67b33cfc57443d0e864885d0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a292778d0cd2d52224c7187f12fc8b9f5eaf9ba32e07c182ab5eaf7189eead73 0.600000000000 1656047 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": 1170328, "vin": [ { "gen": { "height": 1170318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a292778d0cd2d52224c7187f12fc8b9f5eaf9ba32e07c182ab5eaf7189eead73" } } ], "extra": [ 1, 177, 77, 82, 222, 60, 21, 151, 34, 226, 153, 229, 53, 167, 161, 108, 141, 86, 7, 142, 79, 214, 123, 51, 207, 197, 116, 67, 208, 232, 100, 136, 93, 2, 17, 0, 0, 0, 4, 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