Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0deb17106f60ac7d2863cff6ba7d46302d4d6cf390d9b49feed7d317ea80400a

Tx prefix hash: 28442ffc90d7eef57950d5aec2fb79cefa9864e95a5a68ebd7de0111a4fa08f3
Tx public key: ca02c7ec663c1829708d29f388e7b98f85d50ce991f04a0702030b5df1468ea8
Timestamp: 1735667013 Timestamp [UCT]: 2024-12-31 17:43:33 Age [y:d:h:m:s]: 00:323:14:39:30
Block: 1187304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228810 RingCT/type: yes/0
Extra: 01ca02c7ec663c1829708d29f388e7b98f85d50ce991f04a0702030b5df1468ea8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9410012b1006d30e36bf08b39f23f7e942151051cbe458d8c5adc17f0119b2cd 0.600000000000 1673793 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": 1187314, "vin": [ { "gen": { "height": 1187304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9410012b1006d30e36bf08b39f23f7e942151051cbe458d8c5adc17f0119b2cd" } } ], "extra": [ 1, 202, 2, 199, 236, 102, 60, 24, 41, 112, 141, 41, 243, 136, 231, 185, 143, 133, 213, 12, 233, 145, 240, 74, 7, 2, 3, 11, 93, 241, 70, 142, 168, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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