Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0d8656f01044876e4cb4692c4f385780f64b03a194a6b9a24caf5685d8638d7

Tx prefix hash: 74f814716a4427553e1946f56c31fd044cd03a097726a1108785a9f9041b0639
Tx public key: 6513b548fc976870f6d2f82e74d73c8e5f8db79c5378914e497a086f65efdcfc
Timestamp: 1702393617 Timestamp [UCT]: 2023-12-12 15:06:57 Age [y:d:h:m:s]: 01:357:01:11:09
Block: 911607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514063 RingCT/type: yes/0
Extra: 016513b548fc976870f6d2f82e74d73c8e5f8db79c5378914e497a086f65efdcfc021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55e4f31f1d62af0a6374f183e713341b9f8039d8e740ba965a4527f76c372be7 0.600000000000 1368821 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": 911617, "vin": [ { "gen": { "height": 911607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55e4f31f1d62af0a6374f183e713341b9f8039d8e740ba965a4527f76c372be7" } } ], "extra": [ 1, 101, 19, 181, 72, 252, 151, 104, 112, 246, 210, 248, 46, 116, 215, 60, 142, 95, 141, 183, 156, 83, 120, 145, 78, 73, 122, 8, 111, 101, 239, 220, 252, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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