Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9ef97e28ead140496111a88b269051e84d8fd3bd19a11c33bac859ed0418bb4

Tx prefix hash: bbcdcde5d64fe2952d2d378f12566acf33a2883bd444bcfa7271fe17da32b2de
Tx public key: e5934b8761592bbc6a381ff06f2c0de891c8ece4df7bb6e0c076105d18b846a0
Timestamp: 1700766945 Timestamp [UCT]: 2023-11-23 19:15:45 Age [y:d:h:m:s]: 01:069:15:42:11
Block: 898104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310922 RingCT/type: yes/0
Extra: 01e5934b8761592bbc6a381ff06f2c0de891c8ece4df7bb6e0c076105d18b846a002110000000975e3f0e9000000000000000000

1 output(s) for total of 0.648946080000 dcy

stealth address amount amount idx
00: 22066f4912738a794bbb58de2243b8fd10bc5ff93547f0d3fb3b8c98808e3d00 0.648946080000 1354507 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": 898114, "vin": [ { "gen": { "height": 898104 } } ], "vout": [ { "amount": 648946080, "target": { "key": "22066f4912738a794bbb58de2243b8fd10bc5ff93547f0d3fb3b8c98808e3d00" } } ], "extra": [ 1, 229, 147, 75, 135, 97, 89, 43, 188, 106, 56, 31, 240, 111, 44, 13, 232, 145, 200, 236, 228, 223, 123, 182, 224, 192, 118, 16, 93, 24, 184, 70, 160, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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