Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 708ae4c6ab88ba8a800f5fa4a0477cb67b2c1344fb0448aab257b401f68488cc

Tx prefix hash: 366e3207e9018043b01db5d9f517f725b61efbd4c173b27a2037d7896d75fbc9
Tx public key: 147611a2e5459da43d7720fba4fe1cbd87f4fe365c3df77a8a3471556e67bd6a
Timestamp: 1699525981 Timestamp [UCT]: 2023-11-09 10:33:01 Age [y:d:h:m:s]: 01:361:03:10:43
Block: 887821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517000 RingCT/type: yes/0
Extra: 01147611a2e5459da43d7720fba4fe1cbd87f4fe365c3df77a8a3471556e67bd6a02110000000433af99f4000000000000000000

1 output(s) for total of 0.701908459000 dcy

stealth address amount amount idx
00: 525660864765628f1f7b2877d1b0705002762ebb879db50c85ec0d24753fdaf9 0.701908459000 1343722 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": 887831, "vin": [ { "gen": { "height": 887821 } } ], "vout": [ { "amount": 701908459, "target": { "key": "525660864765628f1f7b2877d1b0705002762ebb879db50c85ec0d24753fdaf9" } } ], "extra": [ 1, 20, 118, 17, 162, 229, 69, 157, 164, 61, 119, 32, 251, 164, 254, 28, 189, 135, 244, 254, 54, 92, 61, 247, 122, 138, 52, 113, 85, 110, 103, 189, 106, 2, 17, 0, 0, 0, 4, 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