Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e40c9c9f61d49eff0b7105c2da5b356bfdddd123e297930475df9ebcbe718124

Tx prefix hash: 9f8bcf7dc300662d9859c4b8bfc9635bf5fca8e95785b596f39bb34806f0160e
Tx public key: 342d3b9c45ef4c4af1da2218f9ea7b67e3aad2bf64108f275f87d0b33b43027e
Timestamp: 1578252687 Timestamp [UCT]: 2020-01-05 19:31:27 Age [y:d:h:m:s]: 04:359:05:05:37
Block: 39416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145947 RingCT/type: yes/0
Extra: 01342d3b9c45ef4c4af1da2218f9ea7b67e3aad2bf64108f275f87d0b33b43027e02110000005549b77a3d000000000000000000

1 output(s) for total of 454.368999707000 dcy

stealth address amount amount idx
00: dc3ae2d1be5c83e0b67cf897ed901f27bcae136741154eec69e17ef4d9cbfb1f 454.368999707000 67969 of 0

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": 39426, "vin": [ { "gen": { "height": 39416 } } ], "vout": [ { "amount": 454368999707, "target": { "key": "dc3ae2d1be5c83e0b67cf897ed901f27bcae136741154eec69e17ef4d9cbfb1f" } } ], "extra": [ 1, 52, 45, 59, 156, 69, 239, 76, 74, 241, 218, 34, 24, 249, 234, 123, 103, 227, 170, 210, 191, 100, 16, 143, 39, 95, 135, 208, 179, 59, 67, 2, 126, 2, 17, 0, 0, 0, 85, 73, 183, 122, 61, 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