Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f2064986ac4af2966243d8008127d1f622f349df9470fa5db84cfa6c02be8b6

Tx prefix hash: 5463ac28ad5b7bd9041e719a257619ce282d1f77d1295e8928fa00448cde19bc
Tx public key: c3696d268c3d9f2759a703ac8e4fb0c900b8a44a87dbec972a8b43d882d58245
Timestamp: 1735020784 Timestamp [UCT]: 2024-12-24 06:13:04 Age [y:d:h:m:s]: 00:176:22:07:56
Block: 1181972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126128 RingCT/type: yes/0
Extra: 01c3696d268c3d9f2759a703ac8e4fb0c900b8a44a87dbec972a8b43d882d582450211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d139fa978885726bb913e3e486e65e13a1accf01e894088ccc50f71e0194517 0.600000000000 1668401 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": 1181982, "vin": [ { "gen": { "height": 1181972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d139fa978885726bb913e3e486e65e13a1accf01e894088ccc50f71e0194517" } } ], "extra": [ 1, 195, 105, 109, 38, 140, 61, 159, 39, 89, 167, 3, 172, 142, 79, 176, 201, 0, 184, 164, 74, 135, 219, 236, 151, 42, 139, 67, 216, 130, 213, 130, 69, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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