Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3df9f9ec28cb5e57725a0bf78397d40e7c02d2faddc769225ce79d9cc003ac95

Tx prefix hash: 5d64c96b3551571a749a76549eaedeff26d8cbd5f1e17b11b55c31c8db816587
Tx public key: 66b6aa370e72ac20db56a46c63c53c5e96eb2a966c6034b0a57c884fc827ae5e
Timestamp: 1733025504 Timestamp [UCT]: 2024-12-01 03:58:24 Age [y:d:h:m:s]: 00:110:19:29:57
Block: 1165447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78991 RingCT/type: yes/0
Extra: 0166b6aa370e72ac20db56a46c63c53c5e96eb2a966c6034b0a57c884fc827ae5e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dc251122808f0c7cb426809963865f9c260bf2610c8d44931beb457cc4a2420 0.600000000000 1651122 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": 1165457, "vin": [ { "gen": { "height": 1165447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dc251122808f0c7cb426809963865f9c260bf2610c8d44931beb457cc4a2420" } } ], "extra": [ 1, 102, 182, 170, 55, 14, 114, 172, 32, 219, 86, 164, 108, 99, 197, 60, 94, 150, 235, 42, 150, 108, 96, 52, 176, 165, 124, 136, 79, 200, 39, 174, 94, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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