Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed1b8c5a8f23274302007bce5006938e68b5a0325ae17a469bdf21d2f38cb192

Tx prefix hash: a3b69599b56853df7dfd1089337b632b6814d1c04997b22b52c32f4475ccc4e3
Tx public key: 3e3311e3aaaa4e2aed0e447bd13efbc4ffa0c9288d44dc47a9724482aee191e9
Timestamp: 1712498686 Timestamp [UCT]: 2024-04-07 14:04:46 Age [y:d:h:m:s]: 01:039:06:11:06
Block: 995337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289060 RingCT/type: yes/0
Extra: 013e3311e3aaaa4e2aed0e447bd13efbc4ffa0c9288d44dc47a9724482aee191e902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93cf3826a0c42bb96bcef651b0ddfef6ee692a4cc864ba47d1e21eadb31f557e 0.600000000000 1455745 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": 995347, "vin": [ { "gen": { "height": 995337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93cf3826a0c42bb96bcef651b0ddfef6ee692a4cc864ba47d1e21eadb31f557e" } } ], "extra": [ 1, 62, 51, 17, 227, 170, 170, 78, 42, 237, 14, 68, 123, 209, 62, 251, 196, 255, 160, 201, 40, 141, 68, 220, 71, 169, 114, 68, 130, 174, 225, 145, 233, 2, 17, 0, 0, 0, 7, 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