Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be7ffa8ee10d95cc4e83df11b068b828d0826fe92c013298faadc6838d7ad241

Tx prefix hash: c33b61849b41f1d0ae65447bc2dfb47830df39f0a6a3106a972d38c51a38b8e3
Tx public key: 09b24cedac7202f2d53ff0aaf5dcc99d716eeb2148658d4b73e1463eb5f874de
Timestamp: 1707198467 Timestamp [UCT]: 2024-02-06 05:47:47 Age [y:d:h:m:s]: 01:132:11:39:59
Block: 951412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355690 RingCT/type: yes/0
Extra: 0109b24cedac7202f2d53ff0aaf5dcc99d716eeb2148658d4b73e1463eb5f874de0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18252d99b13132729474af571e384626a5d99f915eae067516c138e032e47a43 0.600000000000 1410174 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": 951422, "vin": [ { "gen": { "height": 951412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18252d99b13132729474af571e384626a5d99f915eae067516c138e032e47a43" } } ], "extra": [ 1, 9, 178, 76, 237, 172, 114, 2, 242, 213, 63, 240, 170, 245, 220, 201, 157, 113, 110, 235, 33, 72, 101, 141, 75, 115, 225, 70, 62, 181, 248, 116, 222, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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