Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2250f4ab439d9b3f1a89f73fb6181556d895c75f91c84eb753191348c9fbbb7

Tx prefix hash: 848f929a806a7a819c38dc61e5a34d756a2d1601192e8fbaa1355629f3e9e3c0
Tx public key: 9dda75c47d8ce7a9e409c5c9ae81b78971894303ec5f4f6d9af909c801c11df5
Timestamp: 1750405612 Timestamp [UCT]: 2025-06-20 07:46:52 Age [y:d:h:m:s]: 00:153:14:03:26
Block: 1308899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107615 RingCT/type: yes/0
Extra: 019dda75c47d8ce7a9e409c5c9ae81b78971894303ec5f4f6d9af909c801c11df5021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47e3c6dca43e86df262d2f88dae8564edc2463342f03d75e12f0183da5da8127 0.600000000000 1796514 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": 1308909, "vin": [ { "gen": { "height": 1308899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47e3c6dca43e86df262d2f88dae8564edc2463342f03d75e12f0183da5da8127" } } ], "extra": [ 1, 157, 218, 117, 196, 125, 140, 231, 169, 228, 9, 197, 201, 174, 129, 183, 137, 113, 137, 67, 3, 236, 95, 79, 109, 154, 249, 9, 200, 1, 193, 29, 245, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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