Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5c21dfdafce0dd9ef9323a10c5e45d6231c6fdaa554c2dac3707685aa8f9b63

Tx prefix hash: d46570abbdf0d4ce438920a1ea0a9f102300d0c4dc3f189855e40ee1a172be7e
Tx public key: 66f8bee076a8564b6c62d334b6f60b86f15757048dbf9cc65503a2db8be07404
Timestamp: 1710511240 Timestamp [UCT]: 2024-03-15 14:00:40 Age [y:d:h:m:s]: 01:006:23:24:54
Block: 978908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265948 RingCT/type: yes/0
Extra: 0166f8bee076a8564b6c62d334b6f60b86f15757048dbf9cc65503a2db8be0740402110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0d15d1754331eda3ec602be7650229de54109caf14183e1b1397bcdac322b24 0.600000000000 1438937 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": 978918, "vin": [ { "gen": { "height": 978908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0d15d1754331eda3ec602be7650229de54109caf14183e1b1397bcdac322b24" } } ], "extra": [ 1, 102, 248, 190, 224, 118, 168, 86, 75, 108, 98, 211, 52, 182, 246, 11, 134, 241, 87, 87, 4, 141, 191, 156, 198, 85, 3, 162, 219, 139, 224, 116, 4, 2, 17, 0, 0, 0, 8, 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