Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d85ec39c9e27d09c9b1e18db98597f46a68e7afe5f8101d8bbe895727e7be435

Tx prefix hash: 861d357a5373910598b8df3308002e998c0d69b9557098e2d9740103ed406437
Tx public key: 1f89af5c4ee58f2a61dee6da012e5f118ab5b72a0f8094b1d90438849a3ff1be
Timestamp: 1705549817 Timestamp [UCT]: 2024-01-18 03:50:17 Age [y:d:h:m:s]: 01:087:21:50:28
Block: 937729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323939 RingCT/type: yes/0
Extra: 011f89af5c4ee58f2a61dee6da012e5f118ab5b72a0f8094b1d90438849a3ff1be02110000002e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fcfb27a5e8bbfb66fff59c0c8fcc1a064f46dbfc2ee89c738850d3966dabe97 0.600000000000 1395791 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": 937739, "vin": [ { "gen": { "height": 937729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fcfb27a5e8bbfb66fff59c0c8fcc1a064f46dbfc2ee89c738850d3966dabe97" } } ], "extra": [ 1, 31, 137, 175, 92, 78, 229, 143, 42, 97, 222, 230, 218, 1, 46, 95, 17, 138, 181, 183, 42, 15, 128, 148, 177, 217, 4, 56, 132, 154, 63, 241, 190, 2, 17, 0, 0, 0, 46, 89, 218, 211, 245, 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