Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdab3f32bf8bad18e24e2e686fe6b13ad3a3dea4e7f17d6056ebcab1129b51f1

Tx prefix hash: c2dd6e96cd66d5cc1073d9628326ed8e85de037b6e2cb31fe308c119bf2e4270
Tx public key: 8a66952bbf32913a4ee317b3f82e573614c6589373c5571cfc3b312cc873f280
Timestamp: 1700495743 Timestamp [UCT]: 2023-11-20 15:55:43 Age [y:d:h:m:s]: 01:167:11:44:02
Block: 895853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380895 RingCT/type: yes/0
Extra: 018a66952bbf32913a4ee317b3f82e573614c6589373c5571cfc3b312cc873f2800211000000024b8f5122000000000000000000

1 output(s) for total of 0.660187222000 dcy

stealth address amount amount idx
00: 4b12caa3fc93da383e09e3703d402c6367258f1be19c2379fa571b863684cc48 0.660187222000 1352100 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": 895863, "vin": [ { "gen": { "height": 895853 } } ], "vout": [ { "amount": 660187222, "target": { "key": "4b12caa3fc93da383e09e3703d402c6367258f1be19c2379fa571b863684cc48" } } ], "extra": [ 1, 138, 102, 149, 43, 191, 50, 145, 58, 78, 227, 23, 179, 248, 46, 87, 54, 20, 198, 88, 147, 115, 197, 87, 28, 252, 59, 49, 44, 200, 115, 242, 128, 2, 17, 0, 0, 0, 2, 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