Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd92eeb79124a8c909da084073e4769630bb112487e448aff3077a3f3acbaab4

Tx prefix hash: 6fe078e60b23b606f05c3fb59c7942d40ee7d5f742b3713888c2f7036ae28c30
Tx public key: ac6fcd7f8e6c02407cc5f21a260e388084a5f2b4a72080f35a722555a5291faf
Timestamp: 1743353285 Timestamp [UCT]: 2025-03-30 16:48:05 Age [y:d:h:m:s]: 00:282:20:52:05
Block: 1250669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199980 RingCT/type: yes/0
Extra: 01ac6fcd7f8e6c02407cc5f21a260e388084a5f2b4a72080f35a722555a5291faf0211000000021a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2a17ec3775dc731e456c2d0812d8a5e0471bfb73819326c2b7ac4e8096dcda0 0.600000000000 1737720 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": 1250679, "vin": [ { "gen": { "height": 1250669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2a17ec3775dc731e456c2d0812d8a5e0471bfb73819326c2b7ac4e8096dcda0" } } ], "extra": [ 1, 172, 111, 205, 127, 142, 108, 2, 64, 124, 197, 242, 26, 38, 14, 56, 128, 132, 165, 242, 180, 167, 32, 128, 243, 90, 114, 37, 85, 165, 41, 31, 175, 2, 17, 0, 0, 0, 2, 26, 151, 4, 3, 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