Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2aedcf58b0aa01c8e3bfae7426011ac059558d2109062074e629950508abe994

Tx prefix hash: 10a455adf349a2a45102395c3b186fd295a98fbb8d95e81947d06ef631bf228a
Tx public key: 2e3a3e355c7cecda5e7abb287ab917f29e9bfa5648c2764da15c86408079b86d
Timestamp: 1732629751 Timestamp [UCT]: 2024-11-26 14:02:31 Age [y:d:h:m:s]: 00:113:09:34:51
Block: 1162163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80874 RingCT/type: yes/0
Extra: 012e3a3e355c7cecda5e7abb287ab917f29e9bfa5648c2764da15c86408079b86d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a183cf83e4bac2d8a77f163735b996da16be9f98594d3fb524bdd0e19ed834b7 0.600000000000 1647818 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": 1162173, "vin": [ { "gen": { "height": 1162163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a183cf83e4bac2d8a77f163735b996da16be9f98594d3fb524bdd0e19ed834b7" } } ], "extra": [ 1, 46, 58, 62, 53, 92, 124, 236, 218, 94, 122, 187, 40, 122, 185, 23, 242, 158, 155, 250, 86, 72, 194, 118, 77, 161, 92, 134, 64, 128, 121, 184, 109, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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