Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f819391dd5650503730b392315ae590928226f56b1f4591d14d907fc34ed8f1e

Tx prefix hash: 5e59c45f11d301fe2cc04965834242b8b4b0420e904385bc6380ef107fba97c7
Tx public key: b3fab44a7e0e34a5649639264ed571ab69cb3bb2fb1bb1e4a0f4312bb9b1d0f9
Timestamp: 1636192218 Timestamp [UCT]: 2021-11-06 09:50:18 Age [y:d:h:m:s]: 03:128:13:37:49
Block: 368492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870243 RingCT/type: yes/0
Extra: 01b3fab44a7e0e34a5649639264ed571ab69cb3bb2fb1bb1e4a0f4312bb9b1d0f902110000000942b3953e000000000000000000

1 output(s) for total of 36.900600373000 dcy

stealth address amount amount idx
00: f6f67647b22303bcb8984826e37daf4952e300f5140ac99c7691fc9f443ac378 36.900600373000 747386 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": 368502, "vin": [ { "gen": { "height": 368492 } } ], "vout": [ { "amount": 36900600373, "target": { "key": "f6f67647b22303bcb8984826e37daf4952e300f5140ac99c7691fc9f443ac378" } } ], "extra": [ 1, 179, 250, 180, 74, 126, 14, 52, 165, 100, 150, 57, 38, 78, 213, 113, 171, 105, 203, 59, 178, 251, 27, 177, 228, 160, 244, 49, 43, 185, 177, 208, 249, 2, 17, 0, 0, 0, 9, 66, 179, 149, 62, 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