Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0cf197326481c189f8639f7a1d3e3c88dda0d648fe8bf2e488506fd87a7e070

Tx prefix hash: a46e0d5dc31b48060dd8f9ccd6482009f2776d213093bdf42df74519a9106e6f
Tx public key: 84134a74d4e7e7269e30ec4f888c79aa4e44cfbe9054de4cb174ea81660d8e6c
Timestamp: 1727906887 Timestamp [UCT]: 2024-10-02 22:08:07 Age [y:d:h:m:s]: 01:037:05:06:22
Block: 1123113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284973 RingCT/type: yes/0
Extra: 0184134a74d4e7e7269e30ec4f888c79aa4e44cfbe9054de4cb174ea81660d8e6c021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 136864140d2c66eaab87e7ce5820f7c67285329d1d872498ccdc4bee9173ccfb 0.600000000000 1605646 of 15

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": 1123123, "vin": [ { "gen": { "height": 1123113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "136864140d2c66eaab87e7ce5820f7c67285329d1d872498ccdc4bee9173ccfb" } } ], "extra": [ 1, 132, 19, 74, 116, 212, 231, 231, 38, 158, 48, 236, 79, 136, 140, 121, 170, 78, 68, 207, 190, 144, 84, 222, 76, 177, 116, 234, 129, 102, 13, 142, 108, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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