Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32f174634a984d061b63c24e44321ba56a034154d5531aa9e39c3b1e6e94a182

Tx prefix hash: a6ba34589ed5490c673d541eb3f0d3574823ed89bfa91ccff1c09b93afd38ecd
Tx public key: d8fdd67972017ad859c30a075a1ffb8ffd293cd3db339915a8172d1c7fe044e5
Timestamp: 1708277329 Timestamp [UCT]: 2024-02-18 17:28:49 Age [y:d:h:m:s]: 01:067:02:14:25
Block: 960370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308998 RingCT/type: yes/0
Extra: 01d8fdd67972017ad859c30a075a1ffb8ffd293cd3db339915a8172d1c7fe044e50211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff936e31c23d6c447a5d677cf49982733cfe8e13235a48bd4ca31d4ed1e6539a 0.600000000000 1419933 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": 960380, "vin": [ { "gen": { "height": 960370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff936e31c23d6c447a5d677cf49982733cfe8e13235a48bd4ca31d4ed1e6539a" } } ], "extra": [ 1, 216, 253, 214, 121, 114, 1, 122, 216, 89, 195, 10, 7, 90, 31, 251, 143, 253, 41, 60, 211, 219, 51, 153, 21, 168, 23, 45, 28, 127, 224, 68, 229, 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