Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2437e3e8707eaf7c0c4227b484aa9d026bc3f853093632c47e838f2cb99b6232

Tx prefix hash: dd8684e3fe2c70507d0301c22adfb3d324a849d8700d9475c3558563b527efa3
Tx public key: fcc3ee40f778f56c06a81ffb7c0d269684fbb9f3701734cac8249f838b6bf7a4
Timestamp: 1705032669 Timestamp [UCT]: 2024-01-12 04:11:09 Age [y:d:h:m:s]: 01:045:12:45:46
Block: 933451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293618 RingCT/type: yes/0
Extra: 01fcc3ee40f778f56c06a81ffb7c0d269684fbb9f3701734cac8249f838b6bf7a40211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ff53d2f59b38de15d706a97cc433b52b024781e49df8e7c954d140e6bea3fb9 0.600000000000 1391413 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": 933461, "vin": [ { "gen": { "height": 933451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ff53d2f59b38de15d706a97cc433b52b024781e49df8e7c954d140e6bea3fb9" } } ], "extra": [ 1, 252, 195, 238, 64, 247, 120, 245, 108, 6, 168, 31, 251, 124, 13, 38, 150, 132, 251, 185, 243, 112, 23, 52, 202, 200, 36, 159, 131, 139, 107, 247, 164, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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