Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1965b8d4c0af953be2085f3969a2f879060097154cf829386ae2c9dd2ea89b8

Tx prefix hash: 383c8f0ab41baffaba152f98e4a390c5a9594709edc6e40353ed5ee0ebe8e9cf
Tx public key: f4866e066c04315c59b0af6312a66f98f1701e1adf0639bf4cb0f12436cdc7e2
Timestamp: 1726319471 Timestamp [UCT]: 2024-09-14 13:11:11 Age [y:d:h:m:s]: 00:270:07:36:50
Block: 1109949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193049 RingCT/type: yes/0
Extra: 01f4866e066c04315c59b0af6312a66f98f1701e1adf0639bf4cb0f12436cdc7e202110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40a0067968bef46e45fb94a0909840d903d356b87cc8c0904a7322d0e4717c92 0.600000000000 1588380 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": 1109959, "vin": [ { "gen": { "height": 1109949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40a0067968bef46e45fb94a0909840d903d356b87cc8c0904a7322d0e4717c92" } } ], "extra": [ 1, 244, 134, 110, 6, 108, 4, 49, 92, 89, 176, 175, 99, 18, 166, 111, 152, 241, 112, 30, 26, 223, 6, 57, 191, 76, 176, 241, 36, 54, 205, 199, 226, 2, 17, 0, 0, 0, 13, 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