Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d427ddcb7b5fd227a0b880ed72cfe1958f540591b649a9c47288f3ab8f273a69

Tx prefix hash: f27e78080c13567dacaa37585d3e027e3835bb6ea7bee170878716dd9ef895d0
Tx public key: 31badf7185f0f4a5bf4a0ef096c24b251e8596260608ac39632360bd31defe8f
Timestamp: 1697233885 Timestamp [UCT]: 2023-10-13 21:51:25 Age [y:d:h:m:s]: 01:245:20:41:52
Block: 869013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436697 RingCT/type: yes/0
Extra: 0131badf7185f0f4a5bf4a0ef096c24b251e8596260608ac39632360bd31defe8f021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.810213015000 dcy

stealth address amount amount idx
00: d757cda0e0a67e42160742f6fbf7abdcdd072c78daf9d354c08a660ec293a19f 0.810213015000 1323840 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": 869023, "vin": [ { "gen": { "height": 869013 } } ], "vout": [ { "amount": 810213015, "target": { "key": "d757cda0e0a67e42160742f6fbf7abdcdd072c78daf9d354c08a660ec293a19f" } } ], "extra": [ 1, 49, 186, 223, 113, 133, 240, 244, 165, 191, 74, 14, 240, 150, 194, 75, 37, 30, 133, 150, 38, 6, 8, 172, 57, 99, 35, 96, 189, 49, 222, 254, 143, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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