Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dbf30eaad38c564e3a569cb0189ba38974db8ed74e871c03c46964bb419d72c

Tx prefix hash: 944c406b511bd07f709f6ff16cb2e0809ff2eb6075277f48f9f86ed48aea75db
Tx public key: 9ce19f5680c9aae514c2f60e50653ab8d783c826ef1869e5bfe2c47a1490d108
Timestamp: 1725157649 Timestamp [UCT]: 2024-09-01 02:27:29 Age [y:d:h:m:s]: 01:129:15:22:27
Block: 1100311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351183 RingCT/type: yes/0
Extra: 019ce19f5680c9aae514c2f60e50653ab8d783c826ef1869e5bfe2c47a1490d108021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e68d9792edc2eebef1db57e205ad111e1eab25f3eb9c8909733aa98e5eeab1fb 0.600000000000 1576286 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": 1100321, "vin": [ { "gen": { "height": 1100311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e68d9792edc2eebef1db57e205ad111e1eab25f3eb9c8909733aa98e5eeab1fb" } } ], "extra": [ 1, 156, 225, 159, 86, 128, 201, 170, 229, 20, 194, 246, 14, 80, 101, 58, 184, 215, 131, 200, 38, 239, 24, 105, 229, 191, 226, 196, 122, 20, 144, 209, 8, 2, 17, 0, 0, 0, 8, 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