Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbb3e03c2b8fdf4d598ddd817dfdda3682da08f819190ada4033e36d4115ea17

Tx prefix hash: 430032af9f23c7eb3110bcb2596625ac4fd970b95ed9a9e715d5b83cf84fefe3
Tx public key: 1ff59169de2a3d4fcc6f05b1eb37f7b2a5bb7e21eeb494e761404a7c0294ad1c
Timestamp: 1580783196 Timestamp [UCT]: 2020-02-04 02:26:36 Age [y:d:h:m:s]: 05:040:23:30:41
Block: 57991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181539 RingCT/type: yes/0
Extra: 011ff59169de2a3d4fcc6f05b1eb37f7b2a5bb7e21eeb494e761404a7c0294ad1c0211000000038a2ee0d9000000000000000000

1 output(s) for total of 394.323413853000 dcy

stealth address amount amount idx
00: e39f9bc34a90151ad60671041af0459477489012f0d055d93c10df6b8f5fb91f 394.323413853000 107258 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": 58001, "vin": [ { "gen": { "height": 57991 } } ], "vout": [ { "amount": 394323413853, "target": { "key": "e39f9bc34a90151ad60671041af0459477489012f0d055d93c10df6b8f5fb91f" } } ], "extra": [ 1, 31, 245, 145, 105, 222, 42, 61, 79, 204, 111, 5, 177, 235, 55, 247, 178, 165, 187, 126, 33, 238, 180, 148, 231, 97, 64, 74, 124, 2, 148, 173, 28, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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