Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7dbe373a76ce894d1a901b9e1e275bb4296b013bdac4eef24ac4b1d1244f33d

Tx prefix hash: c8eadf94f6759113555cb53dd18110f8781fd243a7a232c524f46c374eb69bc5
Tx public key: 298f009fa30bebdb6f0a64cc05b8ae5548f9544a4edbc0f969569c88a33f91bb
Timestamp: 1762939841 Timestamp [UCT]: 2025-11-12 09:30:41 Age [y:d:h:m:s]: 00:049:20:29:57
Block: 1410420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35699 RingCT/type: yes/0
Extra: 01298f009fa30bebdb6f0a64cc05b8ae5548f9544a4edbc0f969569c88a33f91bb021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b4e4c507f590d610a5ccd334b98b65343bd8c674ab81c6a4959391fd9c67245 0.600000000000 1898871 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": 1410430, "vin": [ { "gen": { "height": 1410420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b4e4c507f590d610a5ccd334b98b65343bd8c674ab81c6a4959391fd9c67245" } } ], "extra": [ 1, 41, 143, 0, 159, 163, 11, 235, 219, 111, 10, 100, 204, 5, 184, 174, 85, 72, 249, 84, 74, 78, 219, 192, 249, 105, 86, 156, 136, 163, 63, 145, 187, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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