Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec0351cc7b85b1eccd7aea48f16ad07f3d2cc22229f688465726c35c1b4870cc

Tx prefix hash: f66acc58d35044b798fcb8f2ab687ce43c3c9b3c4439e0595d7c37bc2a09843e
Tx public key: f2066de812f5414debccbd66e3e3b7282d4b18ab05600197d6c3133e737c4d36
Timestamp: 1755175186 Timestamp [UCT]: 2025-08-14 12:39:46 Age [y:d:h:m:s]: 00:052:12:43:34
Block: 1346654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37027 RingCT/type: yes/0
Extra: 01f2066de812f5414debccbd66e3e3b7282d4b18ab05600197d6c3133e737c4d36021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f52cf164caf085d905155505d9c3b3b92c6f940a976161a811d7edbf1346e6e 0.600000000000 1834555 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": 1346664, "vin": [ { "gen": { "height": 1346654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f52cf164caf085d905155505d9c3b3b92c6f940a976161a811d7edbf1346e6e" } } ], "extra": [ 1, 242, 6, 109, 232, 18, 245, 65, 77, 235, 204, 189, 102, 227, 227, 183, 40, 45, 75, 24, 171, 5, 96, 1, 151, 214, 195, 19, 62, 115, 124, 77, 54, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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