Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4088f3864f6a06739cd6483333f1528d8eaecc3cb083af2cbd7654660f66705

Tx prefix hash: f7847051c5bbb461ac2aa3a3edbb8b4df0bb8fa3477d0c1d2ad352a84db39e02
Tx public key: 63259daa1bd9c1e0829f265ad4d35dd7ddb7fd278fffe21ee3f355437b9604ee
Timestamp: 1704726990 Timestamp [UCT]: 2024-01-08 15:16:30 Age [y:d:h:m:s]: 01:162:00:43:47
Block: 930922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376839 RingCT/type: yes/0
Extra: 0163259daa1bd9c1e0829f265ad4d35dd7ddb7fd278fffe21ee3f355437b9604ee02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a55dd3d3f4d023799eb67ffba95708d6f31aa39e5ad975971a69b704b15a1c5d 0.600000000000 1388812 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": 930932, "vin": [ { "gen": { "height": 930922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a55dd3d3f4d023799eb67ffba95708d6f31aa39e5ad975971a69b704b15a1c5d" } } ], "extra": [ 1, 99, 37, 157, 170, 27, 217, 193, 224, 130, 159, 38, 90, 212, 211, 93, 215, 221, 183, 253, 39, 143, 255, 226, 30, 227, 243, 85, 67, 123, 150, 4, 238, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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