Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27d8453685885ab81a3c68545634941a001a66e7b10ea9249dc0ea6e11f7feca

Tx prefix hash: e8b5db5d12c419f7f267b25a723ccbbf4d5333d5f7390c96784c879148663b63
Tx public key: 8691d26a298fd4eb77eaa96b762d412399d170ebee8dca2ee517b19650a4f6ee
Timestamp: 1736682947 Timestamp [UCT]: 2025-01-12 11:55:47 Age [y:d:h:m:s]: 00:065:23:41:44
Block: 1195722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46952 RingCT/type: yes/0
Extra: 018691d26a298fd4eb77eaa96b762d412399d170ebee8dca2ee517b19650a4f6ee0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be6b0a9f550e3f41bc5e0c6169765db8b8186544f2f9b1ac117625072347e0d7 0.600000000000 1682315 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": 1195732, "vin": [ { "gen": { "height": 1195722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be6b0a9f550e3f41bc5e0c6169765db8b8186544f2f9b1ac117625072347e0d7" } } ], "extra": [ 1, 134, 145, 210, 106, 41, 143, 212, 235, 119, 234, 169, 107, 118, 45, 65, 35, 153, 209, 112, 235, 238, 141, 202, 46, 229, 23, 177, 150, 80, 164, 246, 238, 2, 17, 0, 0, 0, 1, 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