Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d99c7222298c4a0d5fa62065ce16e3221aca81ab2c2d8801375f95d0eadecbe

Tx prefix hash: 6c8044d998ed2efd35786dc3e68b1d56d3ad1571f12256a1e3d670cb0733759c
Tx public key: dfadcb43711181363070f8512a8c7beb39a8cc7b10f7f3245b413fb4fe8fda72
Timestamp: 1702913989 Timestamp [UCT]: 2023-12-18 15:39:49 Age [y:d:h:m:s]: 01:115:11:07:17
Block: 915902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343658 RingCT/type: yes/0
Extra: 01dfadcb43711181363070f8512a8c7beb39a8cc7b10f7f3245b413fb4fe8fda7202110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef73ad8579287a074a2fd8e88bc263406fdb00a329da31670a9febdd9b05f21f 0.600000000000 1373336 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": 915912, "vin": [ { "gen": { "height": 915902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef73ad8579287a074a2fd8e88bc263406fdb00a329da31670a9febdd9b05f21f" } } ], "extra": [ 1, 223, 173, 203, 67, 113, 17, 129, 54, 48, 112, 248, 81, 42, 140, 123, 235, 57, 168, 204, 123, 16, 247, 243, 36, 91, 65, 63, 180, 254, 143, 218, 114, 2, 17, 0, 0, 0, 1, 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