Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1321e6613b9c7122b848c764637851ddddb483143826bd00b8724b35ccfa1fa

Tx prefix hash: c193ac9a8723b7994c706f715d80dd6c9353ed32ebf3e90ca065f3bb8473c7c0
Tx public key: e96cdd1b8c357c081976fdcb0ea09cb077a5e1a2efdcc4df501769b084517151
Timestamp: 1717046753 Timestamp [UCT]: 2024-05-30 05:25:53 Age [y:d:h:m:s]: 00:154:16:06:38
Block: 1033078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110706 RingCT/type: yes/0
Extra: 01e96cdd1b8c357c081976fdcb0ea09cb077a5e1a2efdcc4df501769b08451715102110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18cbc6b7d37d6571a87755533455acba5012b079273052152f1947e612d195d3 0.600000000000 1501537 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": 1033088, "vin": [ { "gen": { "height": 1033078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18cbc6b7d37d6571a87755533455acba5012b079273052152f1947e612d195d3" } } ], "extra": [ 1, 233, 108, 221, 27, 140, 53, 124, 8, 25, 118, 253, 203, 14, 160, 156, 176, 119, 165, 225, 162, 239, 220, 196, 223, 80, 23, 105, 176, 132, 81, 113, 81, 2, 17, 0, 0, 0, 10, 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