Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 383943981048b8ac8d8a6d3ec81bdd488f04a61445e44363036b2a65d70be71c

Tx prefix hash: 2cafc42f1c6e4f635823d0abd72eedf34fed669a73cc4cb70db73eb6cfd1ded8
Tx public key: bf42b6b58b724e4b79f20763b6448db093dd4b298e6c035b078af2aa1ca8587d
Timestamp: 1712650509 Timestamp [UCT]: 2024-04-09 08:15:09 Age [y:d:h:m:s]: 00:219:19:02:57
Block: 996597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157369 RingCT/type: yes/0
Extra: 01bf42b6b58b724e4b79f20763b6448db093dd4b298e6c035b078af2aa1ca8587d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b139068bc1e0b87c73d9a98f066d3b6a7a3b92937ae3b219b2dc21acc6d6137 0.600000000000 1457019 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": 996607, "vin": [ { "gen": { "height": 996597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b139068bc1e0b87c73d9a98f066d3b6a7a3b92937ae3b219b2dc21acc6d6137" } } ], "extra": [ 1, 191, 66, 182, 181, 139, 114, 78, 75, 121, 242, 7, 99, 182, 68, 141, 176, 147, 221, 75, 41, 142, 108, 3, 91, 7, 138, 242, 170, 28, 168, 88, 125, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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