Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edbb603a39e3ad9fc9d487d92c53207de5a847a0e969b4f9e1650b15df259dd7

Tx prefix hash: 020cf35e44290b9d211f56553cf7e91a360efd20657de1c1621b6868ede0b7b1
Tx public key: a8e9613f42adb0a3b2316b50464e4f57ae640407e9da6a136ea17c205eec12ec
Timestamp: 1751341702 Timestamp [UCT]: 2025-07-01 03:48:22 Age [y:d:h:m:s]: 00:214:14:20:35
Block: 1316302 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151473 RingCT/type: yes/0
Extra: 01a8e9613f42adb0a3b2316b50464e4f57ae640407e9da6a136ea17c205eec12ec0211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00fda3723fd23143580a48637058f49f2b0ac3e34350b9c98c219510a29495bc 0.600000000000 1803961 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": 1316312, "vin": [ { "gen": { "height": 1316302 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00fda3723fd23143580a48637058f49f2b0ac3e34350b9c98c219510a29495bc" } } ], "extra": [ 1, 168, 233, 97, 63, 66, 173, 176, 163, 178, 49, 107, 80, 70, 78, 79, 87, 174, 100, 4, 7, 233, 218, 106, 19, 110, 161, 124, 32, 94, 236, 18, 236, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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