Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 300c1e5f850d682e50d3aa567572a2c4ee78d303d1246636b652abbafdddb4b7

Tx prefix hash: 466dc986dfc05c14b39006595213775e78c3197c8e0e251b999db864c9c512b5
Tx public key: e8cf74c97aed793b423f4f0ca3ac7bcef3146f032932fba2406c2313bb4cd1ba
Timestamp: 1674436366 Timestamp [UCT]: 2023-01-23 01:12:46 Age [y:d:h:m:s]: 02:128:03:57:34
Block: 680685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 613288 RingCT/type: yes/0
Extra: 01e8cf74c97aed793b423f4f0ca3ac7bcef3146f032932fba2406c2313bb4cd1ba0211000000015029cbac000000000000000000

1 output(s) for total of 3.408850624000 dcy

stealth address amount amount idx
00: 1dec4f216692060548d67a51e21d31f24e42d3c4b74ded4efa7e6f1d2900bfc4 3.408850624000 1122744 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": 680695, "vin": [ { "gen": { "height": 680685 } } ], "vout": [ { "amount": 3408850624, "target": { "key": "1dec4f216692060548d67a51e21d31f24e42d3c4b74ded4efa7e6f1d2900bfc4" } } ], "extra": [ 1, 232, 207, 116, 201, 122, 237, 121, 59, 66, 63, 79, 12, 163, 172, 123, 206, 243, 20, 111, 3, 41, 50, 251, 162, 64, 108, 35, 19, 187, 76, 209, 186, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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