Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c2592cde83872d4c5260256e56bf16fa3b593264aeb5b5df2cbc7c5d25090ab

Tx prefix hash: 3483157ef42584cd58658a2d7bdc4cab05a6e117ea25069f2c23696e3af1b49d
Tx public key: c0c8a53612486e27b0155909d3cd6a364d53e4d35f5783abfb31dccf840d2a38
Timestamp: 1730030555 Timestamp [UCT]: 2024-10-27 12:02:35 Age [y:d:h:m:s]: 01:019:18:42:32
Block: 1140677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272527 RingCT/type: yes/0
Extra: 01c0c8a53612486e27b0155909d3cd6a364d53e4d35f5783abfb31dccf840d2a380211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8635434a5e49deec79d35face1da0be5fa5bba48b913a14b351d7314dadfdba1 0.600000000000 1624478 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": 1140687, "vin": [ { "gen": { "height": 1140677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8635434a5e49deec79d35face1da0be5fa5bba48b913a14b351d7314dadfdba1" } } ], "extra": [ 1, 192, 200, 165, 54, 18, 72, 110, 39, 176, 21, 89, 9, 211, 205, 106, 54, 77, 83, 228, 211, 95, 87, 131, 171, 251, 49, 220, 207, 132, 13, 42, 56, 2, 17, 0, 0, 0, 1, 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