Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51693b4fd3dfaa54fc3a4aa68aecaccc193338508c58ca6b1a1fa34bdb225bea

Tx prefix hash: cf2382ad1bf2411834fdee264c183a18a939c9ebcb91a6d474a56ecd0934ebad
Tx public key: ba64a2a6b77bf19b4488a0d2355ce4a421b50b723afc41bb5e14495bcc679905
Timestamp: 1716936737 Timestamp [UCT]: 2024-05-28 22:52:17 Age [y:d:h:m:s]: 00:228:12:09:18
Block: 1032155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163541 RingCT/type: yes/0
Extra: 01ba64a2a6b77bf19b4488a0d2355ce4a421b50b723afc41bb5e14495bcc67990502110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3accf96b8f3ce08c34f65bcde61d16e95ca1d5187b00c4a86d1ba0116ceb85a 0.600000000000 1500604 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": 1032165, "vin": [ { "gen": { "height": 1032155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3accf96b8f3ce08c34f65bcde61d16e95ca1d5187b00c4a86d1ba0116ceb85a" } } ], "extra": [ 1, 186, 100, 162, 166, 183, 123, 241, 155, 68, 136, 160, 210, 53, 92, 228, 164, 33, 181, 11, 114, 58, 252, 65, 187, 94, 20, 73, 91, 204, 103, 153, 5, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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