Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a84b43c301408ec87e7c184c8e2d97c5eb046de0a5949270befd99648b5372a

Tx prefix hash: baa8e817833aec642c6f5e3e388bc672c6806a4bed3a04f6b05a4560118afc7b
Tx public key: f35e3c060f357c14a4a78d11bef2215116422463fcf5efcbf56f3d25229e45b9
Timestamp: 1712620183 Timestamp [UCT]: 2024-04-08 23:49:43 Age [y:d:h:m:s]: 01:034:23:57:59
Block: 996345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286017 RingCT/type: yes/0
Extra: 01f35e3c060f357c14a4a78d11bef2215116422463fcf5efcbf56f3d25229e45b902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 326c0e22e986b9b44470a07e3a98075da2ef1c3547dafd29d2b7102f325f5c4e 0.600000000000 1456763 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": 996355, "vin": [ { "gen": { "height": 996345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "326c0e22e986b9b44470a07e3a98075da2ef1c3547dafd29d2b7102f325f5c4e" } } ], "extra": [ 1, 243, 94, 60, 6, 15, 53, 124, 20, 164, 167, 141, 17, 190, 242, 33, 81, 22, 66, 36, 99, 252, 245, 239, 203, 245, 111, 61, 37, 34, 158, 69, 185, 2, 17, 0, 0, 0, 2, 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