Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa81f498002c1d9d04e37de4f23f4b0791c05590abc28ebeb8b1d77d96d10526

Tx prefix hash: 9b303edc59d10eed6a21af15f65e6f6c516d77fde3340fd4186ca28f4a88a26e
Tx public key: 4def5626ee28cd83850c051242463c4d3fc378b8ea72e7fe9542e3f0cb0ee2ab
Timestamp: 1731765576 Timestamp [UCT]: 2024-11-16 13:59:36 Age [y:d:h:m:s]: 00:216:07:56:54
Block: 1155004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154314 RingCT/type: yes/0
Extra: 014def5626ee28cd83850c051242463c4d3fc378b8ea72e7fe9542e3f0cb0ee2ab02110000001b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e18da51d4f7e6f57d043e0d7234e3de50a8c8ef7b176b7e0d4ea0d9d28bfb6f7 0.600000000000 1640617 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": 1155014, "vin": [ { "gen": { "height": 1155004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e18da51d4f7e6f57d043e0d7234e3de50a8c8ef7b176b7e0d4ea0d9d28bfb6f7" } } ], "extra": [ 1, 77, 239, 86, 38, 238, 40, 205, 131, 133, 12, 5, 18, 66, 70, 60, 77, 63, 195, 120, 184, 234, 114, 231, 254, 149, 66, 227, 240, 203, 14, 226, 171, 2, 17, 0, 0, 0, 27, 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