Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 305a66447770f7f152f8e95ae4d433d37903b3db43bd4040a8b6b7ec906db76c

Tx prefix hash: 51d110db8e615c744b65975fa762f9ca9d6176685e0f6afd2e3856cac0c0ee92
Tx public key: 96f4d4f6cc48a5a21362042291ff2422cdfb1f44d753e4be7e7f209c8e438719
Timestamp: 1752590684 Timestamp [UCT]: 2025-07-15 14:44:44 Age [y:d:h:m:s]: 00:129:09:41:57
Block: 1326083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91224 RingCT/type: yes/0
Extra: 0196f4d4f6cc48a5a21362042291ff2422cdfb1f44d753e4be7e7f209c8e438719021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1ce671f15aa61c6ee629fe80b8c801916cc36ef5a3940ed350c772474f4380d 0.600000000000 1813832 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": 1326093, "vin": [ { "gen": { "height": 1326083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1ce671f15aa61c6ee629fe80b8c801916cc36ef5a3940ed350c772474f4380d" } } ], "extra": [ 1, 150, 244, 212, 246, 204, 72, 165, 162, 19, 98, 4, 34, 145, 255, 36, 34, 205, 251, 31, 68, 215, 83, 228, 190, 126, 127, 32, 156, 142, 67, 135, 25, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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