Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37cefc69093ab91d55d23ba4fd6cb6447cf3c4a4473ee56e8bff82537c915245

Tx prefix hash: fc80a8ab852e3e669b3a772a5ec0ab465d282ac7e80b9d7eab66e9cba90d72a3
Tx public key: a63ab1b33ba6d7ce9365b6cb7c87c8748006a40851aea566f5426dc7b34202e9
Timestamp: 1702278137 Timestamp [UCT]: 2023-12-11 07:02:17 Age [y:d:h:m:s]: 01:334:15:02:10
Block: 910624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498033 RingCT/type: yes/0
Extra: 01a63ab1b33ba6d7ce9365b6cb7c87c8748006a40851aea566f5426dc7b34202e90211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e89240f057182408300e8ff8e54a02c57ad73c1284234de7da5f826610a55c77 0.600000000000 1367785 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": 910634, "vin": [ { "gen": { "height": 910624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e89240f057182408300e8ff8e54a02c57ad73c1284234de7da5f826610a55c77" } } ], "extra": [ 1, 166, 58, 177, 179, 59, 166, 215, 206, 147, 101, 182, 203, 124, 135, 200, 116, 128, 6, 164, 8, 81, 174, 165, 102, 245, 66, 109, 199, 179, 66, 2, 233, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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