Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 832c8aa2c6ea9e0f38bbe1b2941d7991604fefd5263bee6cbb96afea1bc55b55

Tx prefix hash: 7e25e5bf5ad1ad40e0f5b9088c981086a75a3d54a262214f0705d7a05f949f17
Tx public key: c5383c9ff212b8ece854d07719bc428cfb983479a284993e9038db3a8eefe9cc
Timestamp: 1716748577 Timestamp [UCT]: 2024-05-26 18:36:17 Age [y:d:h:m:s]: 00:157:20:47:18
Block: 1030609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112989 RingCT/type: yes/0
Extra: 01c5383c9ff212b8ece854d07719bc428cfb983479a284993e9038db3a8eefe9cc02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee16061102bc5b03f697196ccd1c993cc82b9a53dad9d4e20a9067e23c6f46f1 0.600000000000 1498866 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": 1030619, "vin": [ { "gen": { "height": 1030609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee16061102bc5b03f697196ccd1c993cc82b9a53dad9d4e20a9067e23c6f46f1" } } ], "extra": [ 1, 197, 56, 60, 159, 242, 18, 184, 236, 232, 84, 208, 119, 25, 188, 66, 140, 251, 152, 52, 121, 162, 132, 153, 62, 144, 56, 219, 58, 142, 239, 233, 204, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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