Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d68c724985ce95e2c7ac55333807b6da4da36cfe0da44c837fdbb84eddfa884

Tx prefix hash: 50c47d6e99f2d64e147cf80af81b51e3233a642220b5b5bb5fe794ff73b0ff28
Tx public key: 2e797f38d9d899e3a6006b821e714bda03a252f9be23b6f87c1e465493c46318
Timestamp: 1750638793 Timestamp [UCT]: 2025-06-23 00:33:13 Age [y:d:h:m:s]: 00:151:18:31:45
Block: 1310790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106358 RingCT/type: yes/0
Extra: 012e797f38d9d899e3a6006b821e714bda03a252f9be23b6f87c1e465493c46318021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d9ec4aed11d29708bcc5e4188ec1aefcbf07ca10e4f32e43b4c0ec9ee66ffa2 0.600000000000 1798413 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": 1310800, "vin": [ { "gen": { "height": 1310790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d9ec4aed11d29708bcc5e4188ec1aefcbf07ca10e4f32e43b4c0ec9ee66ffa2" } } ], "extra": [ 1, 46, 121, 127, 56, 217, 216, 153, 227, 166, 0, 107, 130, 30, 113, 75, 218, 3, 162, 82, 249, 190, 35, 182, 248, 124, 30, 70, 84, 147, 196, 99, 24, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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