Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ce56bfa766cf1fdd7abcd1a09f7b8083c5b52efce2e2e392e768cc4c5c3d6a1

Tx prefix hash: f5477127d25cfc012a6895e6dbf571310a4fb573d92063410340436c81ec4e8b
Tx public key: e479a95ab6d924c09ecfaa3e5840ee44d60d0afc39f41a72a84bdc77cf5b8d3e
Timestamp: 1724707630 Timestamp [UCT]: 2024-08-26 21:27:10 Age [y:d:h:m:s]: 01:150:16:28:24
Block: 1096567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366079 RingCT/type: yes/0
Extra: 01e479a95ab6d924c09ecfaa3e5840ee44d60d0afc39f41a72a84bdc77cf5b8d3e021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6742824f90225d49a8b21f372e8367c4d42d126c587fb134e3457754570bc77 0.600000000000 1571758 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": 1096577, "vin": [ { "gen": { "height": 1096567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6742824f90225d49a8b21f372e8367c4d42d126c587fb134e3457754570bc77" } } ], "extra": [ 1, 228, 121, 169, 90, 182, 217, 36, 192, 158, 207, 170, 62, 88, 64, 238, 68, 214, 13, 10, 252, 57, 244, 26, 114, 168, 75, 220, 119, 207, 91, 141, 62, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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