Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e394e93dc3e28179135c80350cbad4b0f167834002ac9d3159d7ef0a0e2af0d

Tx prefix hash: dec3fa777b9224dbb5012b23125d1d3b7acf35b27645319b6cb12b0841022502
Tx public key: 94e349f0cb507802444c88e0724073d670b551b77e9bdd7f76e5e2a5ab3d8e15
Timestamp: 1730393965 Timestamp [UCT]: 2024-10-31 16:59:25 Age [y:d:h:m:s]: 00:081:21:03:55
Block: 1143646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58534 RingCT/type: yes/0
Extra: 0194e349f0cb507802444c88e0724073d670b551b77e9bdd7f76e5e2a5ab3d8e15021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 494ca96f654b68c73873033bc38ceb2f42c758824bd85685207b2e3ed3fe9a35 0.600000000000 1627587 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": 1143656, "vin": [ { "gen": { "height": 1143646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "494ca96f654b68c73873033bc38ceb2f42c758824bd85685207b2e3ed3fe9a35" } } ], "extra": [ 1, 148, 227, 73, 240, 203, 80, 120, 2, 68, 76, 136, 224, 114, 64, 115, 214, 112, 181, 81, 183, 126, 155, 221, 127, 118, 229, 226, 165, 171, 61, 142, 21, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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