Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fb356f40d814a8839590b35aa541f5535f0d83a7798d4f11addbfb79bf55903

Tx prefix hash: 171f085a23900b035e786deec3aef953463df34bf021d1b78b6af3951a35ab6b
Tx public key: 8d0982a77308f18e5e03667439b721f4fd9c4e386d25c9181adfbbb85cc966f6
Timestamp: 1760298611 Timestamp [UCT]: 2025-10-12 19:50:11 Age [y:d:h:m:s]: 00:085:03:58:04
Block: 1388533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61001 RingCT/type: yes/0
Extra: 018d0982a77308f18e5e03667439b721f4fd9c4e386d25c9181adfbbb85cc966f6021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fe2925ae23a38f91704d0336fd08834669448930db5a94aef9ab6e0024bcfbb 0.600000000000 1876748 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": 1388543, "vin": [ { "gen": { "height": 1388533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fe2925ae23a38f91704d0336fd08834669448930db5a94aef9ab6e0024bcfbb" } } ], "extra": [ 1, 141, 9, 130, 167, 115, 8, 241, 142, 94, 3, 102, 116, 57, 183, 33, 244, 253, 156, 78, 56, 109, 37, 201, 24, 26, 223, 187, 184, 92, 201, 102, 246, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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