Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf43f16b95e624f95fda9e1e0f1cdd64bc710bdecbe4186515b83b163d7e66a5

Tx prefix hash: a1dc6ac44d1d6c57adbc5a2608f37cf20058b7648387db9bb6ffc6a92264b31c
Tx public key: ad39ed8b054b1d004988627b018c9f4e6c0d09eb7319147a0c8981a2cb7d992d
Timestamp: 1707568609 Timestamp [UCT]: 2024-02-10 12:36:49 Age [y:d:h:m:s]: 01:329:03:37:19
Block: 954485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494105 RingCT/type: yes/0
Extra: 01ad39ed8b054b1d004988627b018c9f4e6c0d09eb7319147a0c8981a2cb7d992d02110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01e033f8d08fef09ef35c0d72fc6e04fa8e511a77f49ab8e8034a98e332d740e 0.600000000000 1413765 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": 954495, "vin": [ { "gen": { "height": 954485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01e033f8d08fef09ef35c0d72fc6e04fa8e511a77f49ab8e8034a98e332d740e" } } ], "extra": [ 1, 173, 57, 237, 139, 5, 75, 29, 0, 73, 136, 98, 123, 1, 140, 159, 78, 108, 13, 9, 235, 115, 25, 20, 122, 12, 137, 129, 162, 203, 125, 153, 45, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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