Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc38a746dc552af6f03085d54123b78471d0137c7a457f30caff9945ec7b7611

Tx prefix hash: 3f64f1c2c99d9db5f79170ad39902cc671284d2f4c8f97dad1f185a9a9fd25f2
Tx public key: 7ef3f2686a42eeb5c18abf24950c0250bd2b510d82d9b79f10c2beffb07f383c
Timestamp: 1766263239 Timestamp [UCT]: 2025-12-20 20:40:39 Age [y:d:h:m:s]: 00:002:16:09:18
Block: 1437970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1898 RingCT/type: yes/0
Extra: 017ef3f2686a42eeb5c18abf24950c0250bd2b510d82d9b79f10c2beffb07f383c0211000000047b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fd635a425bdf092c259d3a57f59638ef135b2e217838d3cfa463ce3cce44e86 0.600000000000 1926783 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": 1437980, "vin": [ { "gen": { "height": 1437970 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fd635a425bdf092c259d3a57f59638ef135b2e217838d3cfa463ce3cce44e86" } } ], "extra": [ 1, 126, 243, 242, 104, 106, 66, 238, 181, 193, 138, 191, 36, 149, 12, 2, 80, 189, 43, 81, 13, 130, 217, 183, 159, 16, 194, 190, 255, 176, 127, 56, 60, 2, 17, 0, 0, 0, 4, 123, 30, 81, 172, 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