Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77a16a4d0db549ed7051fc7be79932577066059868d7bbaf2e50182a01878aff

Tx prefix hash: babdf9d54385b83d2be658e6b888f84027edbadc67cb9dc276f72a4abdef4a1b
Tx public key: 8dc3f2ff5a65e4aef3ae01c51fa2a9cbb7b7605a020f3b014855fcb4565b8425
Timestamp: 1698310842 Timestamp [UCT]: 2023-10-26 09:00:42 Age [y:d:h:m:s]: 01:159:07:32:49
Block: 877963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374849 RingCT/type: yes/0
Extra: 018dc3f2ff5a65e4aef3ae01c51fa2a9cbb7b7605a020f3b014855fcb4565b84250211000000034b8f5122000000000000000000

1 output(s) for total of 0.756735550000 dcy

stealth address amount amount idx
00: ba140f5e68087a1584e5b8d5fc1ffdae0bc4da4add23c48eae42a2deb3b4c51a 0.756735550000 1333367 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": 877973, "vin": [ { "gen": { "height": 877963 } } ], "vout": [ { "amount": 756735550, "target": { "key": "ba140f5e68087a1584e5b8d5fc1ffdae0bc4da4add23c48eae42a2deb3b4c51a" } } ], "extra": [ 1, 141, 195, 242, 255, 90, 101, 228, 174, 243, 174, 1, 197, 31, 162, 169, 203, 183, 183, 96, 90, 2, 15, 59, 1, 72, 85, 252, 180, 86, 91, 132, 37, 2, 17, 0, 0, 0, 3, 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