Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeb7add68c4b01542341998f7e90934ca1e2e536e0c7701f147f01b8be66aeb2

Tx prefix hash: c232d9ef38abc685d9cd7179b5e4b0570b6ab4f83c3bcae42b45a4a055173b8a
Tx public key: 32fed2606a9d8faa5a2c01eeb52e3e40a17d156a0ac80461a3666e3ac6330c83
Timestamp: 1722822739 Timestamp [UCT]: 2024-08-05 01:52:19 Age [y:d:h:m:s]: 00:228:15:39:39
Block: 1080950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163315 RingCT/type: yes/0
Extra: 0132fed2606a9d8faa5a2c01eeb52e3e40a17d156a0ac80461a3666e3ac6330c83021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45455ae035b305a11882c46eb90032c4efac51e98bc8b889d1e691a683f8b751 0.600000000000 1554509 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": 1080960, "vin": [ { "gen": { "height": 1080950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45455ae035b305a11882c46eb90032c4efac51e98bc8b889d1e691a683f8b751" } } ], "extra": [ 1, 50, 254, 210, 96, 106, 157, 143, 170, 90, 44, 1, 238, 181, 46, 62, 64, 161, 125, 21, 106, 10, 200, 4, 97, 163, 102, 110, 58, 198, 51, 12, 131, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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