Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ec5d0a69546303661dcc59d7b7a8262461ad3f3bcaf4890bb71133202834783

Tx prefix hash: ce1f290c04a0febe90ca308745a4f153c29fb70c2d18e924f5d53ea41b58d3cf
Tx public key: 5d2e3240f4f8c899d0fd7c9e6b94b550f95f8ff965a114c51bb2a81a28f1f4c1
Timestamp: 1712538027 Timestamp [UCT]: 2024-04-08 01:00:27 Age [y:d:h:m:s]: 01:213:06:35:07
Block: 995662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411124 RingCT/type: yes/0
Extra: 015d2e3240f4f8c899d0fd7c9e6b94b550f95f8ff965a114c51bb2a81a28f1f4c102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe7a3370bd37d7f4f47d9a2996dd70d0f0e2754b50e126b1f9410eb8d905e4c7 0.600000000000 1456076 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": 995672, "vin": [ { "gen": { "height": 995662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe7a3370bd37d7f4f47d9a2996dd70d0f0e2754b50e126b1f9410eb8d905e4c7" } } ], "extra": [ 1, 93, 46, 50, 64, 244, 248, 200, 153, 208, 253, 124, 158, 107, 148, 181, 80, 249, 95, 143, 249, 101, 161, 20, 197, 27, 178, 168, 26, 40, 241, 244, 193, 2, 17, 0, 0, 0, 1, 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