Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56b0f9bcf6c4d8767719de6ee69a3c1ccd74d259ea7943680a9d4d40a0d370f0

Tx prefix hash: dc7e55ea30ebe3c0b2d003aca7cae1622af52fbf76bfdc4a10345097cb0c10f4
Tx public key: 805bb63c4b579ef89a78c2e7762f45dd90dbb8a4a5e0f7e1989417b615d4b8ca
Timestamp: 1710450219 Timestamp [UCT]: 2024-03-14 21:03:39 Age [y:d:h:m:s]: 01:014:14:03:10
Block: 978404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271392 RingCT/type: yes/0
Extra: 01805bb63c4b579ef89a78c2e7762f45dd90dbb8a4a5e0f7e1989417b615d4b8ca0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8288da4eee1e1431dae60bf88b27f4ce59220c11a1c237e38319b8d8154279a 0.600000000000 1438431 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": 978414, "vin": [ { "gen": { "height": 978404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8288da4eee1e1431dae60bf88b27f4ce59220c11a1c237e38319b8d8154279a" } } ], "extra": [ 1, 128, 91, 182, 60, 75, 87, 158, 248, 154, 120, 194, 231, 118, 47, 69, 221, 144, 219, 184, 164, 165, 224, 247, 225, 152, 148, 23, 182, 21, 212, 184, 202, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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