Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21097802d81017220b5003bbd2e7658d9d137defee10ba22a400c0c790bed9ba

Tx prefix hash: 61bb1c7c0d4211859f59b5131ae4f60dfa05a1d8e990db4a77b15428f2be0118
Tx public key: a3b7fb6971e3720c196545f9c026a88705c82e457a92d208c1d007d3097b0d36
Timestamp: 1735353186 Timestamp [UCT]: 2024-12-28 02:33:06 Age [y:d:h:m:s]: 00:125:05:13:01
Block: 1184713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89303 RingCT/type: yes/0
Extra: 01a3b7fb6971e3720c196545f9c026a88705c82e457a92d208c1d007d3097b0d360211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b04940b43829e11bd3be7347dce577ae465ab49f068ea01a9ac73ba2bf22f9f 0.600000000000 1671172 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": 1184723, "vin": [ { "gen": { "height": 1184713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b04940b43829e11bd3be7347dce577ae465ab49f068ea01a9ac73ba2bf22f9f" } } ], "extra": [ 1, 163, 183, 251, 105, 113, 227, 114, 12, 25, 101, 69, 249, 192, 38, 168, 135, 5, 200, 46, 69, 122, 146, 210, 8, 193, 208, 7, 211, 9, 123, 13, 54, 2, 17, 0, 0, 0, 7, 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