Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0dcb14eb5359f1fd8c4a9b2817ad359a9cde71f5acbe079d97d01cb180a5d2b

Tx prefix hash: a76cab2b2c95917303db2ca2aa8c2d1d3b85474ac985f248a5c41f7112743553
Tx public key: e88321e5b13b57ab8b063d666775c485e8b794bddf09032c8cdeb05ffa644921
Timestamp: 1695632190 Timestamp [UCT]: 2023-09-25 08:56:30 Age [y:d:h:m:s]: 01:113:19:38:47
Block: 855734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342624 RingCT/type: yes/0
Extra: 01e88321e5b13b57ab8b063d666775c485e8b794bddf09032c8cdeb05ffa6449210211000000054b8f5122000000000000000000

1 output(s) for total of 0.896598637000 dcy

stealth address amount amount idx
00: 0a2329fa511fe0d14199ce40299a1e5198ecf488c80b1c1fc9c793b6ef63d7e0 0.896598637000 1309772 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": 855744, "vin": [ { "gen": { "height": 855734 } } ], "vout": [ { "amount": 896598637, "target": { "key": "0a2329fa511fe0d14199ce40299a1e5198ecf488c80b1c1fc9c793b6ef63d7e0" } } ], "extra": [ 1, 232, 131, 33, 229, 177, 59, 87, 171, 139, 6, 61, 102, 103, 117, 196, 133, 232, 183, 148, 189, 223, 9, 3, 44, 140, 222, 176, 95, 250, 100, 73, 33, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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