Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80f809003e89a87b10e27b7cc5ccaa2f546c5ed493743454edcd0e86493e5461

Tx prefix hash: 230565cd534c966e6df6d64c2c4259a3e3ecccbe3b1ff65827f7cbf3c26c13ad
Tx public key: 655147d5a3f7f965c49ca9fbec2b3691055a5da21280743f5d6e5accf81c244e
Timestamp: 1717160684 Timestamp [UCT]: 2024-05-31 13:04:44 Age [y:d:h:m:s]: 00:307:07:57:23
Block: 1034021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219637 RingCT/type: yes/0
Extra: 01655147d5a3f7f965c49ca9fbec2b3691055a5da21280743f5d6e5accf81c244e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2ac2d75551890e8919f18b74ca9f3d04941ffaacffd0df2973d769f033b3ee7 0.600000000000 1502494 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": 1034031, "vin": [ { "gen": { "height": 1034021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2ac2d75551890e8919f18b74ca9f3d04941ffaacffd0df2973d769f033b3ee7" } } ], "extra": [ 1, 101, 81, 71, 213, 163, 247, 249, 101, 196, 156, 169, 251, 236, 43, 54, 145, 5, 90, 93, 162, 18, 128, 116, 63, 93, 110, 90, 204, 248, 28, 36, 78, 2, 17, 0, 0, 0, 1, 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