Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90f79b75b66e568f9e11184b4fdabb18e69f21dee59a0ed75a6510deeb357da9

Tx prefix hash: 91c42a730f91e2bcc0243ec07c2d6d9cec34f1e6b51b49649889f7290f0feea2
Tx public key: 8c221213f522777f81d348c938c5c5c8e1d4d3d2357021b90ccf464a48d468e1
Timestamp: 1763976540 Timestamp [UCT]: 2025-11-24 09:29:00 Age [y:d:h:m:s]: 00:045:06:50:50
Block: 1419012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32428 RingCT/type: yes/0
Extra: 018c221213f522777f81d348c938c5c5c8e1d4d3d2357021b90ccf464a48d468e102110000000517b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05c7b4579345030954229b2f603bc2e253485026c71a1fcc8052625a7d22f180 0.600000000000 1907547 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": 1419022, "vin": [ { "gen": { "height": 1419012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05c7b4579345030954229b2f603bc2e253485026c71a1fcc8052625a7d22f180" } } ], "extra": [ 1, 140, 34, 18, 19, 245, 34, 119, 127, 129, 211, 72, 201, 56, 197, 197, 200, 225, 212, 211, 210, 53, 112, 33, 185, 12, 207, 70, 74, 72, 212, 104, 225, 2, 17, 0, 0, 0, 5, 23, 177, 145, 50, 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