Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faa3e5ed26f0ea15563367b66bc15385deab1a4421b0bd2f3a4f4d68c2f6ed9a

Tx prefix hash: 9a889e8e858bc79c0bf8b1769f47e54c476a67d6928b2d91a1a6f93587217d1c
Tx public key: 6a385fb62096ffae3ba419ad89a8295d09dc004c5b60bc34b3ffc6b897e14f90
Timestamp: 1697158117 Timestamp [UCT]: 2023-10-13 00:48:37 Age [y:d:h:m:s]: 01:174:17:41:36
Block: 868380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385923 RingCT/type: yes/0
Extra: 016a385fb62096ffae3ba419ad89a8295d09dc004c5b60bc34b3ffc6b897e14f900211000000014b8f5122000000000000000000

1 output(s) for total of 0.814135342000 dcy

stealth address amount amount idx
00: 4b7de8a2df5f59d2d55e147823ad4dd106146c45cdd4e740bf40bb2162b5df30 0.814135342000 1323187 of 0

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": 868390, "vin": [ { "gen": { "height": 868380 } } ], "vout": [ { "amount": 814135342, "target": { "key": "4b7de8a2df5f59d2d55e147823ad4dd106146c45cdd4e740bf40bb2162b5df30" } } ], "extra": [ 1, 106, 56, 95, 182, 32, 150, 255, 174, 59, 164, 25, 173, 137, 168, 41, 93, 9, 220, 0, 76, 91, 96, 188, 52, 179, 255, 198, 184, 151, 225, 79, 144, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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