Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a6e3825e335baaffe225676b8b1f0bf70bea9f656637d1666974f026ff8e3ec

Tx prefix hash: 7a6ac5b39449ff83a29075c685360b58161a5d8b208bbfa11f9cdd2d0e843644
Tx public key: 01f30b60e5abb365ecf8e88a020742972666620af6cc05782fcc9fb8f9a5a443
Timestamp: 1696063681 Timestamp [UCT]: 2023-09-30 08:48:01 Age [y:d:h:m:s]: 01:192:18:49:49
Block: 859318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398837 RingCT/type: yes/0
Extra: 0101f30b60e5abb365ecf8e88a020742972666620af6cc05782fcc9fb8f9a5a443021100000017e6d27f9c000000000000000000

1 output(s) for total of 0.872414327000 dcy

stealth address amount amount idx
00: 084139bc3f83ddb7c803596ddef8530bcf21bb3bc10e1954f2542c6d9ccd2bc0 0.872414327000 1313538 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": 859328, "vin": [ { "gen": { "height": 859318 } } ], "vout": [ { "amount": 872414327, "target": { "key": "084139bc3f83ddb7c803596ddef8530bcf21bb3bc10e1954f2542c6d9ccd2bc0" } } ], "extra": [ 1, 1, 243, 11, 96, 229, 171, 179, 101, 236, 248, 232, 138, 2, 7, 66, 151, 38, 102, 98, 10, 246, 204, 5, 120, 47, 204, 159, 184, 249, 165, 164, 67, 2, 17, 0, 0, 0, 23, 230, 210, 127, 156, 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