Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5de3c27569566f5b90bf7be4c740926982aec07bea293c0f89e023a2873ccd12

Tx prefix hash: 82b8b00125ed18387455a53ab60233ed15988211e53096e2fa26e1dcf8c3a43f
Tx public key: b8fa7244b518abc9738ae31b72b28c74b9ad0f6520ef5622ad7aa29021562b2b
Timestamp: 1683610252 Timestamp [UCT]: 2023-05-09 05:30:52 Age [y:d:h:m:s]: 01:336:16:54:51
Block: 756124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501864 RingCT/type: yes/0
Extra: 01b8fa7244b518abc9738ae31b72b28c74b9ad0f6520ef5622ad7aa29021562b2b02110000000233af99f4000000000000000000

1 output(s) for total of 1.917112064000 dcy

stealth address amount amount idx
00: 35a0418b119e59d7654b30f8725a5182de5d3d589837b5f8c246c4607a56df24 1.917112064000 1204471 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": 756134, "vin": [ { "gen": { "height": 756124 } } ], "vout": [ { "amount": 1917112064, "target": { "key": "35a0418b119e59d7654b30f8725a5182de5d3d589837b5f8c246c4607a56df24" } } ], "extra": [ 1, 184, 250, 114, 68, 181, 24, 171, 201, 115, 138, 227, 27, 114, 178, 140, 116, 185, 173, 15, 101, 32, 239, 86, 34, 173, 122, 162, 144, 33, 86, 43, 43, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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