Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e409831c4a337756c079de41654e3478fccb449332eb9037d79f595d16507cc

Tx prefix hash: d9e91ffb7d2d28884431ac0c53229ce4d4ea2348b237afe0a4fd226fff47238d
Tx public key: adbfed4bd4000342dca549bb5b98b5cfe3f14bbca5f047a58c21d430ab6b3cb3
Timestamp: 1709361590 Timestamp [UCT]: 2024-03-02 06:39:50 Age [y:d:h:m:s]: 01:035:17:10:40
Block: 969357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286522 RingCT/type: yes/0
Extra: 01adbfed4bd4000342dca549bb5b98b5cfe3f14bbca5f047a58c21d430ab6b3cb302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc45d7fc01da90bae515cb2dd08b112148b87e1a2b8c0a0bbf9412940b2e5191 0.600000000000 1429186 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": 969367, "vin": [ { "gen": { "height": 969357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc45d7fc01da90bae515cb2dd08b112148b87e1a2b8c0a0bbf9412940b2e5191" } } ], "extra": [ 1, 173, 191, 237, 75, 212, 0, 3, 66, 220, 165, 73, 187, 91, 152, 181, 207, 227, 241, 75, 188, 165, 240, 71, 165, 140, 33, 212, 48, 171, 107, 60, 179, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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