Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b25ccc5afd8bdd4cc9a8518eef3270e6dba68312ab2df223853591f330d248d

Tx prefix hash: 133a82eb024c0e13e51620270d43db2a60f4faf859919d2c3766529ee06673df
Tx public key: e0b798a936b8202ca91ca9f79a8dd6fcd1e1d0f95da587a1e1691d41c11e17e9
Timestamp: 1758786323 Timestamp [UCT]: 2025-09-25 07:45:23 Age [y:d:h:m:s]: 00:089:12:29:53
Block: 1375996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64100 RingCT/type: yes/0
Extra: 01e0b798a936b8202ca91ca9f79a8dd6fcd1e1d0f95da587a1e1691d41c11e17e9021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82c475b72156998d14d6f6c6059152f012ff95b6eb13d5e460f77961517cd333 0.600000000000 1864087 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": 1376006, "vin": [ { "gen": { "height": 1375996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82c475b72156998d14d6f6c6059152f012ff95b6eb13d5e460f77961517cd333" } } ], "extra": [ 1, 224, 183, 152, 169, 54, 184, 32, 44, 169, 28, 169, 247, 154, 141, 214, 252, 209, 225, 208, 249, 93, 165, 135, 161, 225, 105, 29, 65, 193, 30, 23, 233, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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