Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ef813da100e60081f460150fae84d3744ff1194dc5f2c9a7c0fb9e5562482e4

Tx prefix hash: 0d1d31d3384e6c29a9bf3acb492d9f60b10713e7fc4176ca2652e908c11db041
Tx public key: a2b8c1b0f8874fdc14a8371d464768fd555c413f99e1c7bdb93e3ef7cdefd1e5
Timestamp: 1702104257 Timestamp [UCT]: 2023-12-09 06:44:17 Age [y:d:h:m:s]: 01:190:10:05:01
Block: 909184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397183 RingCT/type: yes/0
Extra: 01a2b8c1b0f8874fdc14a8371d464768fd555c413f99e1c7bdb93e3ef7cdefd1e502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0d649d50e179bda2baf126e3fe07162f85944c0f0100048c9d931f8bafc42b4 0.600000000000 1366253 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": 909194, "vin": [ { "gen": { "height": 909184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0d649d50e179bda2baf126e3fe07162f85944c0f0100048c9d931f8bafc42b4" } } ], "extra": [ 1, 162, 184, 193, 176, 248, 135, 79, 220, 20, 168, 55, 29, 70, 71, 104, 253, 85, 92, 65, 63, 153, 225, 199, 189, 185, 62, 62, 247, 205, 239, 209, 229, 2, 17, 0, 0, 0, 1, 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