Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 603f9dd8f0fcef65682a616709d82ce6f8eff98e540505e32f34244d21e511da

Tx prefix hash: 7230720c33d08ec15f7c8c3d716c4dea9b3518a7b2c22a1d8c5ac77e1bd0bc58
Tx public key: 9501143cfe563fbfcc971fbf4f176b69870e3219bac4f949528ea69c01e45ab4
Timestamp: 1751820249 Timestamp [UCT]: 2025-07-06 16:44:09 Age [y:d:h:m:s]: 00:138:04:33:05
Block: 1320045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97169 RingCT/type: yes/0
Extra: 019501143cfe563fbfcc971fbf4f176b69870e3219bac4f949528ea69c01e45ab402110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc0f5809befd008c0eeac27bd610e4bd3dc5c994a4c609f6d403d06c0cc7e79c 0.600000000000 1807740 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": 1320055, "vin": [ { "gen": { "height": 1320045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc0f5809befd008c0eeac27bd610e4bd3dc5c994a4c609f6d403d06c0cc7e79c" } } ], "extra": [ 1, 149, 1, 20, 60, 254, 86, 63, 191, 204, 151, 31, 191, 79, 23, 107, 105, 135, 14, 50, 25, 186, 196, 249, 73, 82, 142, 166, 156, 1, 228, 90, 180, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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